COMMENT ⊗   VALID 00001 PAGES
C REC  PAGE   DESCRIPTION
C00001 00001
C00002 ENDMK
C⊗;
∂24-Nov-76  1518	RPG  	Debug/Step (SAIL)  
To:   MACLSP.DIS[AID,RPG]:; 
	DEBUG now knows about STEP in that while inspecting
stack frames, DEBUG will ignore all frames associated with the
single stepping facility.

∂26-Nov-76  1324	RPG  	TRACE/STEP(SAIL)   
To:   MACLSP.DIS[AID,RPG]:; 
	The Step package now UNTRACes any function it has to
single step through. Step will print a message informing the luser
of any UNTRACEs performed.
			-rpg-

∂02-Dec-76  1437	RPG  	NCOMPLR/TOPS-10    
To:   MACLSP.DIS[AID,RPG]:; 
	The ncomplr now parses file names in winning line mode.
In addition, full decoding of files is now
available. Thus you can say:
	FOO.FAS[LO,SER]←FOO.LSR[BLE,TCH](KT)
and all will be well.

∂08-Dec-76  1514	RPG  	INPUSH/INPOP/SAIL  
To:   MACLSP.DIS[AID,RPG]:; 
	The SAIL Maclisp now sports INPUSH/INPOP, which can be
used to do stack-structured input. Delicately based on the 
IOPUSH/IOPOP/MTAPE UUO's at SAIL, they can be used as follows:

	***FOO.BAR***
	      .
	      .
	      .
	'CIAO
	(INPUSH LOSING FLE)
	'BACK-AGAIN
	      .
	      .
	      .

	***LOSING.FLE***
	      .
	      .
	      .
	'HI-THERE
	(INPOP)
	      .
	      .
	      .
 
Then (EREAD FOO BAR DSK (LO SER)) produces:
	.
	.
	.
CIAO
(DSK (LO SER))	;value of (INPUSH ...)
	.
	.
	.
HI-THERE
T		;due to (INPOP)
BACK-AGAIN
	.
	.
	.
 
	Notice that (INPOP) has to occur in the file: simply letting
(READ) run off the end fails! To remedy this, there is a function
called REQUIRE (given an autoload property by (HELP), which will
(PRINT (EVAL (READ))) everything in the file which is REQUIRE'ed.
It is called as: (REQUIRE LOSING FLE DSK (LO SER)) i.e. it has
the same arguments as UREAD. The NCOMPLR also knows about REQUIRE,
and the proper thing to do is:
	(DECLARE (EVAL (READ))
	(REQUIRE LOSING FLE DSK (LO SER))
which will work whether the file is being read or compiled.
	I would discourage the use of these functions, however,
since they depend on black UUO magic and will possibly disappear
with the onslaught on NEWIO around Armageddon.

∂26-Feb-77  1624	RPG  	Eread    
To:   MACLSP.DIS[AID,RPG]:; 
	Eread, the E-file understanding version of Uread now accepts the
following:
	(EREAD <file-name> {<ext> default: no extension}{<device> default: DSK}
	  (<proj> {<prog> default: prog of dskppn}))
where {} indicates optional args and defaults

∂19-May-77  0118	JP  	running E from maclsp    
To:   MACLSP.DIS[AID,RPG]:; 
File ET.FAS[MAC,LSP] contains LSUBR ET that swaps to E from MACLSP.
Permissible incantations are
	(et '(fil))			;uses E default extensions in disk dir
	(et '(fil ext))			;disk dir
	(et '(fil ext (prj prg)))	
	(et '(fil (prj prg)))		;default ext
	(et)				;runs E on last file edited
Notice that the device is always assumed to be DSK.
Bugs, comments → JP

∂01-Jul-77  2212	DCO  	MAIL in MACLSP
To:   MACLSP.DIS[AID,RPG]:; 

	MACLSP now accepts mail.   If you have the (HELP) option, type
(MAIL) to enter the mail program.   You will be prompted to give a destination
list and then the message, both of which must be surrounded by double quotes.
Here is an example of its use:

(MAIL)
Destination?  (Any valid MAIL destination list surrounded by "s)
"DCO, RPG%SAIL"
Message?  (surrounded by "s)
"Notice that a message may run over any number of lines and may contain
any characters.    If you want a double quote in your message, type it twice
as in "".    The message now ends."

	It is generally faster to send mail using (MAIL) then to use the MAIL
monitor command because (MAIL) does not start up a separate job.    The tradeoff
is that the mail is not delivered immediately, but waits until the remind
phantom checks if there is any incoming arpanet mail.   This happens roughly
every ten minutes.